Menspesifikasi Metrik Reka Bentuk Dengan Menggunakan Nahu Atribut

Pada awalnya, kajian dalam metrik perisian lebih tertumpu kepada menilai metrik daripada kod sumber. Walau bagaimanapun, metrik tersebut Cuma diperoleh pada fasa terakhir iaitu selepas fasa implementasi. Minat untuk mengekstrak metrik perisian telah berkembang kepada fasa yang lebih awal dalam pembangunan perisian yang digelar sebagai metrik reka bentuk. Kajian telah menunjukkan bahawa metrik reka bentuk jarang digunakan di dalam pengukuran 'projek yang sebenar'. Ini adalah kerana ketidakupayaan untuk mengekstrak metrik reka bentuk secara automatik pada awal projek. Salah satu cara untuk mengekstrak metrik reka bentuk telah diperkenalkan dengan menspesifikasi metrik reka bentuk yang terkenal seperti metrik graf panggilan dan metrik aliran maklumat melalui penggunaan nahu atribut. Nahu atribllt mempunyai kelebihan kerana ia adalah seperti nahu konteks bebas dan mampu menspesifikasi semantik statik bagi bahasa. Ini boleh di gunakan di dalam penspesifikasian penilaian metrik reka bentuk. Dokumen reka bentuk seperti carta struktur diwakilkan secara abstrak oleh bahasa penerangan reka bentuk yang mcngandungi tatatanda clan maklumat reka bentuk. Alat pengkompil UNIX, FLEX dan BISON, digunakan di dalam melaksanakan penilaian dan pungutan metrik reka bentuk

Framework for Aggregating Interactive Multi-Criteria for Web-Based Applications Using Fuzzy Measure and 2-Additive Choquet Integral

Web-based Application (WBA) quality is hard to evaluate because it consists of multiple criteria to be measured. Researchers have developed software quality models that were intended to be comprehensive and applicable to all software development. However, most of the works that focus on the quality model do not reference the aggregation methods used to calculate the values of the different element of the model. In fact, the aggregation methods are not really discussed in the literatures related to software quality. Although the need for a sound methodology is widely recognised, previous researchers generally avoid the use of multi-criteria decision method and mostly dealt with the simplest form of aggregation, which is categorized under additive approach. This approach presents some drawbacks, some do not posses all desirable properties and some seem to be restrictive. As a result they tend to construct independent criteria, or criteria that are supposed to be so, which caused some bias effect in the evaluation. The purpose of this research is to establish a multi-criteria aggregation framework to evaluate WBA that would allow evaluator to incorporate interaction behaviour in the aggregation process. Firstly, the relationships between quality criteria were investigated using survey and correlation studies. The studies have confirmed that there exist positive, negative or neutral relationships between software quality criteria. Based on the relationships identified, the interactions of quality criteria are modelled using fuzzy measure approach. Secondly, the produced fuzzy measures are integrated into the 2-additive Choquet Integral to aggregate the multi quality criteria values. Besides that, the relative importance of each quality factor and the Web preference also play an important role in determining the overall evaluation. Case studies of three different domains of WBA were conducted to validate the proposed aggregation procedure. The overall results of 2-additive Choquet integral are compared against the additive model approach. Consequently, results of the 2-additive Choquet integral have shown that the ranking of overall evaluation results reflect the earlier preference stated by the evaluator compared to the additive model approaches. The fuzzy measure modelling has allowed the incorporation of interaction exist between the quality criteria to be considered in the aggregation process. The results are also consistent with the additive model approach when no interaction exists

Deriving objective navigational measures for web usability

Navigation is one of web usability attribute besides other usability characteristic such as presentation and content. Various navigational measures (metrics) has been proposed to support web usability. However, although there are various navigational metrics available, navigation remains as root of most major web usability problems. Developers are facing difficulties in applying web usability measures due to its ambiguity thus making it prone to different interpretation among developers. While some webs are not affected by the implementation of the misinterpreted measures, some might face much worst usability condition when the misinterpreted measures are applied in the web design. This study aims to propose objective navigational measures for web usability. To ensure the measures acceptability, only dominant measures are filtered in the derivation process. The measures are then implemented in a demo web to demonstrate its applicability

Compatibility of agile software development methods and CMMI

Agile software development methods by focusing on the different values, have established a new approach for software development compare to the traditional methods. While traditional methods emphasizes on the following disciplined processes and rigid practices, agile methods focused on individuals and their collaborations. Previously, CMMI was introduced as process improvement model in the traditional methods and now it is known as symbol of those methods. Nevertheless, compatibility of these two different approaches has been a serious question and there are several conflicting reports about their compatibility. The main purpose of this study was scrutinizing this issue. Generic practices and specific practices in CMMI were selected as criteria for checking compatibility of CMMI and agile methods. The results showed that CMMI and agile are compatible in several process areas. However, there are serious incompatibilities in the others. In level 3 and level 4 of CMMI, two and one incompatible process areas have been seen respectively. Also, agile does not support most of the generic practices in CMMI level 4 and 5. The results also showed that these incompatibilities return to the notion of organization and its role in software development

Evaluation of software quality attributes for Vessel Tracking Management System (VTMS)

Software quality and assurance becomes inevitable as the non-functional requirements continue to gain more popularity than functional requirements. Even some system could resolve some problem, but if nonfunctional requirements been neglected, at that point the solution may be impractical.The system with least features and quality characteristics will lead to low demand and failed-to-market.The aim of this study was to evaluate the quality in use attributes for Vessel Tracking and Management System (VTMS) adopted from the latest ISO/IEC 25010 quality model in the perspective of users’ satisfaction.Five properties of quality in use are explicitly evaluated which are effectiveness, efficiency, satisfaction, freedom from risk and context coverage.A study was conducted through observation and survey to evaluate all five quality in use attributes of VTMS and to explore the relationship between each quality in use attribute to determine the overall users’ satisfaction.Generally, this study provides an early empirical evaluation of the practical value of case study method. Firstly, from the VTMS perspective, the system provide a great 100% in functions coverage (completeness) although there are two (2) functions need to take immediate action in terms of accuracy so make up total 98.4% for effectiveness.On the other hand, the efficiency which measure the response time for each VTMS main tasks was 92.83%.It is concluded that all five (5) quality in use attributes scores more than 75% which are above the MMEA’s minimum requirement on overall users’ satisfaction

Agile transformation: a multi-dimensional process

Software companies are widely interested to use Agile methodologies instead of traditional methods, mainly because of achieving the values offered by Agile approach. However, literature review implies that the alteration process is subject to various serious challenges that make Agile transformation more difficult than expected. Most of the companies are facing these challenges mainly because of the lack of knowledge and understanding of the transformation process. We have conducted a large-scale empirical research study discover various aspects of Agile transformation. Applying a Grounded Theory study identified the general outline of Agile transformation Process. The main aim of this paper is to illustrate the most important concepts that need to be considered when adopting Agile methodologies. This study showed that Agile transformation comprises many concepts, activities, and steps including transformation prerequisites, facilitators, framework, assessment, coaching, and so on. Software companies and organizations need to be familiar with these concepts before inception of Agile transformation process

On the current agile assessment methods and approaches

Agile methods are widely used in software companies in recent years. Many software companies are replacing their traditional development methods with Agile methods. Nonetheless, measuring agility that they have achieved has be topic of debate. So far, only a few methods and tools have been proposed to measure the agility of software companies who are moving to agile. The main aim of this paper is reviewing the existing agile assessment methods and providing a brief discussion on drawbacks of these methods. This paper tries to elucidate the actual position of these methods in measuring agility degree of companies who are moving to agile approach

Crosscutting concern domain library listing composition for early aspect discovery

Modularization is an essential part of a software program that ensures software maintainability. However, object oriented programs still can’t achieve the higher level modularization since it still contain extensive amount of crosscutting concerns. Crosscutting concerns refer to common functionality that does exist in software programs. Separation of concern (SoC) is essential elements of aspect oriented paradigm whereby it has viewed as a way to modularize the existing object oriented programs. Since there are various crosscutting concerns exist, the SoC from base functionality become tedious process. In fact, the process of identifying crosscutting concern for legacy system notably difficult and time consuming. Moreover, crosscutting concern generalization hard to be achieved due to it contain more domain specific concerns. This triggers a need for a literature survey in which it collect and review articles which indicate the usage of crosscutting concerns that exist in software programs in regards of domains. There are five main domains has been specifically retrieved from previous studies. The outcome of the evidence based survey grouped as a domain library which known as Crosscutting Concern Domain Library Listing (CCDLL). CCDLL emphasize on the usage to software practitioner in order to collectively reuse the crosscutting concernswith regards to the domains

Agile transformation: what is it about?

Agile software development by offering new values motivates software companies to use Agile methods instead of traditional methods. However, reviewing the literature shows that leaving traditional methods and moving to Agile methods is subjected to many serious challenges. We have conducted a large-scale research study to empirically discover various aspects of Agile transformation. Our Grounded Theory study showed the general outline of Agile transformation. The main aim of this paper is to figure out the most important concepts that need to be considered when moving to Agile. This study showed that Agile transformation comprises many concepts, activities, and steps including transformation prerequisites, facilitators, framework, assessment, coaching, and so on. Companies need to be familiar with these concepts before starting transitioning to Agile